home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Internet Publisher's Toolbox
/
Internet Publisher's Toolbox.iso
/
w95in
/
rk01_gd.doc
(
.txt
)
< prev
next >
Wrap
Word Document
|
1995-04-09
|
94KB
|
984 lines
Chapter 1
Corporate Deployment Guide
This chapter is for administrators responsible for corporate implementation
of Windows 95 and provides an overview of the significant steps in the
deployment process. Chapter 2, ΓÇ£Corporate Implementation Strategy,ΓÇ¥
contains the details about how to make decisions and perform actions listed
in the overview.
For step-by-step instructions on conducting the installation, see Chapter
3, ΓÇ£Introduction to Windows 95 Setup,ΓÇ¥ and Chapter 5, ΓÇ£Custom, Automated,
and Push Installations,” in the Windows 95 Resource Kit.
A Microsoft Project (.MPP) file is available to use as a template for the
overview and details of deployment planning described in ΓÇ£Corporate
Deployment GuideΓÇ¥ earlier in this chapter and Chapter 2, ΓÇ£Corporate
Implementation Strategy.ΓÇ¥
In This Chapter
Overview of the Process 2
Review Windows 95 3
Assemble the Planning Team and Tools 4
Specify the Preferred Network Client Configuration 5
Conduct the Lab Test 13
Plan the Pilot Rollout 16
Conduct the Pilot Rollout 18
Finalize the Rollout Plan 19
Roll Out Windows 95! 20
Overview of the Process
The deployment process for Windows 95 is divided into distinct phases that
span everything from evaluating the product, to specifying the preferred
network client configuration, and pushing the installation from a central
network server. The following are the suggested phases of deployment:
Review Windows 95
Assemble the planning team and tools
Specify the preferred network client configuration
Conduct the lab test of the client configuration
Plan the pilot rollout
Conduct the pilot rollout
Finalize the rollout plan
Roll out Windows 95
In the sections that describe each phase, checklists are provided to
describe the tasks for the specific phase. Detailed instructions for
performing each task are provided in Chapter 2, ΓÇ£Corporate Implementation
Strategy.ΓÇ¥
The following sample illustrates how to use the checklists at your site.
Description of Deployment Phase
| | | | |
|Task |Team |Start week |Duration |
| | | | |
|1: Summary of the |Who will work |When does |How long will |
|task. |on this task? |this task |it take to |
| | |start? |complete? |
The tasks may vary for your particular organizationΓÇÖs structure and needs.
For the purpose of this guide, individuals performing tasks are grouped in
the following teams, made up of employees from your organization:
The Executive team includes the deployment project manager (usually the
head of the Information Systems department) and members of the executive
committee of the corporation.
The Planning team includes the deployment project manager, key
Installation team members, and a representative from the Support and
Training teams.
The Installation team includes technicians and individuals who will be
conducting the installation.
The Support team includes staff of the help desk or Support department,
and select individuals from the Planning team.
The Training team includes individuals responsible for user training.
Review Windows 95
When Windows 95 is implemented, it can yield significant benefits to your
organization in terms of cost savings and increased system control. Because
many decisions — starting with the decision to acquire Windows 95 — depend
on anticipated benefits, the first step in beginning to plan the rollout
process is to closely examine the new and enhanced features in Windows 95.
Windows 95 is designed to make deployment easy in the corporate
environment.
By understanding how best to plan and automate the installation process,
you
can potentially reduce the cost of migration, making it significantly less
than the migration cost from Windows 3.0 to Windows 3.1! For information on
how Windows 95 reduces migration costs and simplifies the deployment
process,
consult studies from industry analysts such as Gartner Group, Inc., or
information from Microsoft concerning business justifications for
Windows 95.
Review Windows 95 Features
| | | | |
|Task |Team |Start |Duration|
| | |week | |
| | | | |
|1: Read Introducing Microsoft |Executive,|Week 1 |7 days |
|Windows 95 (ISBN 1-55615-860-2) |Planning | | |
|available from Microsoft Press or the | | | |
|Windows 95 Reviewer’s Guide (available| | | |
|from Microsoft WinNews forums on the | | | |
|Internet and other online services). | | | |
|2: If business justification for |Executive,|Week 1 |14 days |
|Windows 95 deployment is required, |Planning | | |
|review total cost of ownership, | | | |
|migration, and productivity studies | | | |
|published by analysts such as Gartner | | | |
|Group, Inc., to assess the impact of | | | |
|Windows 95 on your business’s bottom | | | |
|line. | | | |
|3: Acquire the Windows 95 Resource |Planning |Week 2 |1 day |
|Kit for review during | | | |
|the deployment process. | | | |
Assemble the Planning Team and Tools
After the assigned teams complete the review phase and have a general
perspective on Windows 95 features and benefits, you are ready to assemble
the people and tools needed to plan the Windows 95 implementation; training
of the Support team also takes place during this phase. The tasks for
assembling the resources are described in the following checklist.
Assemble the Planning Team and Tools
| | | | |
|Task |Team |Start |Duratio|
| | |week |n |
| | | | |
|1: Assign the project manager (if |Planning |Week 2 | ΓÇö |
|appropriate; usually this is | | | |
|the head of the Information Systems | | | |
|department). | | | |
|2: Select key Planning and |Planning |Week 2 |5 days |
|Installation team members. | | | |
|3: Acquire Windows 95 (the compact |Planning |Week 2 |1 day |
|disc version is preferred because it | | | |
|contains system administration tools).| | | |
|4: Inventory your client and server |Planning |Week 3 |5 days |
|hardware and software configurations | | | |
|on the network. | | | |
|5: Set up a testing lab. |Planning |Week 2 |1 day |
|6: Acquire test computers for use as|Planning |Week 2 |5 days |
|the network server and clients. Choose| | | |
|computer models that are typical of | | | |
|those | | | |
|used in your organization. | | | |
|7: Install the application software |Planning |Week 3 |3 days |
|and line-of-business tools | | | |
|in the lab to simulate the network | | | |
|environment. Also inventory the | | | |
|mission-critical and non-critical | | | |
|business and other applications | | | |
|typically used in your organization | | | |
|and record them in a checklist to be | | | |
|used during testing. | | | |
|8: Review discussions of product |Planning, |Week 3 |3 days |
|features in the Windows 95 Reviewer’s |Installati| | |
|Guide, and in the ΓÇ£Guided Tour for |on | | |
|Administrators” in the Windows 95 | | | |
|Resource Kit; and study Chapter 2, | | | |
|ΓÇ£Installation,ΓÇ¥ in the Resource Kit. | | | |
|9: Study the entire Windows 95 |Support |Week 3 |10 days|
|Resource Kit. As an option, the | | | |
|Support team (and others as | | | |
|appropriate) can attend training at a | | | |
|Microsoft Authorized Technical | | | |
|Education Center and participate in | | | |
|the Certified Professional program. | | | |
|10: Optionally, read Inside Windows 95|Planning, |Week 2 |10 days|
|from Microsoft Press, |Installati| | |
|for technical details on the inner |on, | | |
|workings of Windows 95. |Support | | |
Specify the Preferred Network Client Configuration
With the Planning team assembled and educated about Windows 95
capabilities, the next step is to specify the preferred configuration for
client computers; this configuration will be used for evaluation and
testing, prior to full implementation. This phase involves documenting the
configuration layout (where Windows 95
files will be located) and determining which features will be used in the
preferred configuration on client computers. (For the purposes of this
discussion, “client computer” refers to any computer running Windows 95,
including computers that act as peer servers by running File and Printer
Sharing services.)
For any given feature or capability, such as the network redirector or a
particular protocol implementation, there are several options to choose
from. Before making
a decision, evaluate the features and consider the alternativesΓÇö including
whether to use them at all. Then choose the appropriate implementation
based on its performance, functionality, and compatibility.
Although you can use other methods to determine the preferred client
configuration, Microsoft recommends that you start from the ΓÇ£idealΓÇ¥
configuration, which uses
all of the most powerful features of Windows 95, and then work backward to
a configuration that may have fewer features but more closely fits your
companyΓÇÖs needs. The selected configuration and any modifications will be
rigorously tested
in the lab before company-wide implementation.
The following tables list the features and capabilities of the ideal
configuration
and related alternatives, plus the chapters where these features are
discussed in
the Resource Kit. Work through this table, checking off the features you
plan
to implement. To learn more about these features, see Chapter 2, ΓÇ£Corporate
Implementation Strategy,ΓÇ¥ or the related Resource Kit chapters.
The last table in this section lists features which Microsoft recommends
for implementation by all organizations.
Configuration Layout Decisions
| | |
|Configuration |Decisions and issues |
|option | |
| | |
|Location of |Depends on your need to maximize |
|Windows files |central security |
|To maximize |and administration versus |
|performance, |performance on the client |
|security, or hard |computer. Also depends on the |
|disk space |hardware platform of the client |
|on the client |computer. |
|computer |Options: |
| |Run Windows 95 on the client |
| |computer for best performance and |
| |reduced network traffic. |
| |Run Windows 95 from the server to |
| |save hard disk space on client |
| |computers and make it easier to |
| |upgrade components or drivers |
| |later, especially for multiple |
| |computers. |
| |Run completely from the server for|
| |the highest degree of security or |
| |for diskless workstations. |
| |For information, see Chapter 4, |
| |ΓÇ£Server-Based Setup for Windows |
| |95.ΓÇ¥ |
Key Features of the Ideal Network Client
| | |
|Preferred feature |Decisions and issues |
| | |
|Use 32-bit, |Depends on the compatibility of |
|protected-mode |your required applications. |
|network client |Options vary based on your |
|software |network. |
|To provide the |For example, for Novell® NetWare® |
|best |networks: |
|network |Protected-mode Client for NetWare |
|performance |Networks |
|and functionality |is the preferred client, because |
| |of the performance and increased |
| |functionality, and because itΓÇÖs |
| |easy |
| |to install and configure. |
| |Real-mode Novell NETX or VLM |
| |clients may offer slightly better |
| |compatibility with some network |
| |utilities. |
| |A real-mode network client for |
| |another network |
| |can also be used. |
| |For information, see Part 3, |
| |ΓÇ£Networking.ΓÇ¥ |
| | |
|Use 32-bit, |Depends on compatibility with your|
|protected-mode |choice of client. Options depend |
|protocols |on your choice of protocol. For |
|To provide the |example, for IPX/SPX: |
|best network |Microsoft IPX/SPX-compatible |
|performance and |protocol is preferred (with or |
|functionality |without IPX over NetBIOS). |
| |Keep real-mode IPXODI for use with|
| |a real-mode Novell-supplied |
| |client. |
| |Both the real-mode and Microsoft |
| |protected-mode implementations can|
| |be used if some of your |
| |applications (such as TSRs) |
| |require the real-mode protocol. |
| |For information, see Chapter 12, |
| |ΓÇ£Network Technical Discussion.ΓÇ¥ |
| | |
|Use the latest |Depends on the availability and |
|network adapter |compatibility of the new driver. |
|drivers |The 32-bit, protected mode drivers|
|To provide |offer vastly improved performance |
|improved perform |and reliability over |
|and the ability to|older versions. For PCMCIA cards, |
|load and unload |the 32-bit drivers are extremely |
|the network and |easy to manage. |
|notify the rest of|Options: |
|the system, use |Always use the newest drivers |
|NDIS 3.1 drivers, |available; implemented by default.|
|which support Plug|Manually choose to keep using an |
|and Play |older driver, including ODI |
| |drivers, if new drivers are not |
| |available. |
| |For information, see Chapter 12, |
| |ΓÇ£Network Technical Discussion.ΓÇ¥ |
Key Features of the Ideal Network Client (continued)
| | |
|Preferred feature |Decisions and issues |
| | |
|Use the new |Depends on timing or preference |
|Windows 95 user |rather than functionality because |
|interface |the new user interface is |
|To provide ease of|significantly more functional and |
|use and maximum |efficient. But, |
|functionality in |if a rapid migration is required, |
|accessing |and training is not immediately |
|Windows 95 |available, the Windows 3.1 user |
|features |interface can be used temporarily |
| |. |
| |Options: |
| |Use the new user interface; this |
| |is preferred and installed by |
| |default. |
| |Install the Windows 3.x File |
| |Manager and Program Manager. |
| |For information, see Chapter 22, |
| |ΓÇ£Program Support.ΓÇ¥ |
Microsoft recommends that you include the following features in your
preferred configuration. These features define how Windows 95 will be
installed and administered in your organization.
Recommended Windows 95 Features for Client Configurations
| | |
|Windows 95 feature|Decisions and issues |
| | |
|Use system |Choose this feature to enable |
|policies |centralized administration or add |
|To enable |control. |
|centralized |Options: |
|administration |Use System Policy Editor to define|
|capabilities of |policies at |
|Windows 95 or add |any time. |
|control of the |For computers running a shared |
|user’s desktop |copy of Windows 95 from a server, |
| |configure the |
| |shared installation directory with|
| |a limited set |
| |of components for Windows 95. This|
| |is not an optimal choice. |
| |For information, see Chapter 15, |
| |ΓÇ£User Profiles and System |
| |Policies.ΓÇ¥ |
Recommended Windows 95 Features for Client Configurations (continued)
| | |
|Windows 95 feature|Decisions and issues |
| | |
|Use user profiles |Choose this feature to maintain |
|To allow multiple |consistent desktop |
|users to use a |and environment settings on a |
|single computer |user-specific basis. Enabling user|
|with their own |profiles causes a slight delay |
|settings or, |during logon. |
|conversely, to |Options: |
|allow personalized|Users can control changes to their|
|settings per user |user profiles |
|on multiple |and update them as they want. |
|computers |Administrators can predefine a |
| |mandatory profile for specific |
| |users, that can only be changed by|
| | |
| |the administrator. |
| |For information, see Chapter 15, |
| |ΓÇ£User Profiles and System |
| |Policies.ΓÇ¥ |
| | |
|Enable remote |Install this service to allow |
|administration |remote administration. To use it, |
|To allow an |you must use a 32-bit network |
|administrator to |client and also enable user-level |
|remotely manage |access. |
|the file system, |For information, see Chapter 16, |
|network sharing, |ΓÇ£Remote Administration.ΓÇ¥ |
|or Registry of the| |
|individual | |
|computers | |
| | |
|Use setup scripts |Choose this feature if you must |
|(batch files) for |install Windows 95 |
|installation |on more than five computers. |
|To allow automated|Server-based Setup offers an easy |
|installation on |to use, graphical |
|client computers |tool for creating setup scripts. |
| |You can also manually create a |
| |script with additional options by |
| |creating a |
| |text file with the appropriate |
| |entries. |
| |For information, see Chapter 5, |
| |ΓÇ£Custom, Automated, and Push |
| |Installations,ΓÇ¥ and Appendix D, |
| |ΓÇ£MSBATCH.INF Parameters.ΓÇ¥ |
| | |
|Set up for push |Choose to use a push installation,|
|installation |based on the location and number |
|To allow the |of computers you must upgrade. |
|administrator to |Options: |
|push the |Edit the login script to run a |
|installation from |setup script. |
|the server without|Use a tool such as the Microsoft |
|touching the |Systems Management Server to |
|client computer |facilitate the setup. |
| |For information, see Chapter 5, |
| |ΓÇ£Custom, Automated, and Push |
| |Installations,ΓÇ¥ and Appendix K, |
| |ΓÇ£Microsoft Systems Management |
| |Server.ΓÇ¥ |
Recommended Windows 95 Features for Client Configurations (continued)
| | |
|Windows 95 feature|Decisions and issues |
| | |
|Use peer resource |Choose this feature based on your |
|sharing services |siteΓÇÖs security |
|To allow a client |needs. If users are allowed to |
|computer |share local resources |
|to share files and|on their computers, then peer |
|resources such as |resource sharing can |
|printers and |save network traffic and hard disk|
|CD-ROM drives with|space on the server. For central |
|other computers |control or to prevent users from |
| |turning on this feature, use |
| |system policies. |
| |This feature can only be installed|
| |on computers that |
| |use a 32-bit, protected-mode |
| |network client. |
| |For information, see Chapter 11, |
| |ΓÇ£Logon, Browsing, and Resource |
| |Sharing.ΓÇ¥ |
| | |
|Use user-level |Choose this feature to enable |
|security |users to specify the users and |
|To implement |groups who have access to local |
|control, by means |shared resources (including the |
|of the logon |Registry). Validation by a |
|process, for a |Windows NT Server or a NetWare |
|variety of |server can also be required before|
|services beyond |access to any resources is |
|network resource |possible under Windows 95. |
|access, including |Options: |
|File and Printer |Users can specify individuals and |
|Sharing, Remote |groups, and their access rights to|
|Registry, backup |shared resources. |
|agents, and other |Users must log on to a server at |
|network and system|startup; user information is |
|management |pulled from a Windows NT domain or|
|functions |a Novell NetWare bindery. |
| |User-level security is required |
| |for remote administration of the |
| |Registry and for network access to|
| |full user profiles. |
| |User-level security requires that |
| |File and Printer Sharing for |
| |Microsoft Networks or NetWare |
| |Networks be loaded. |
| |Share-level security can be used |
| |to share files and printers if no |
| |Windows NT or NetWare server is |
| |available. |
| |For information, see Chapter 14, |
| |ΓÇ£Security.ΓÇ¥ |
The following table lists other features that may be useful to include in
your preferred configuration.
Other Optional Windows 95 Features
| | |
|Windows 95 feature|Decisions and issues |
| | |
|Use Microsoft |Depends on whether you have an |
|Exchange Mail |existing mail system and whether |
|To have a unified |you want the added integration of |
|inbox for |messaging services offered by |
|messages, faxes, |Microsoft Exchange. |
|and so on |Options: |
| |Install all or part of Microsoft |
| |Exchange during |
| |the installation. |
| |Run your existing mail client as |
| |usual. |
| |For information, see Chapter 26, |
| |ΓÇ£Electronic Mail and Microsoft |
| |Exchange.ΓÇ¥ |
| | |
|Use Windows 95 |Depends on the particular hardware|
|mobile computing |and the working needs of mobile |
|features |computing users. Some of these |
|To enable |features are not installed by |
|Windows 95 |default but can be specified |
|features that |during Setup or installed later: |
|support mobile |Dial-Up Networking client software|
|computing or |for dial-up connection to popular |
|switching between |servers |
|portable and |Windows 95 Briefcase for |
|docking station |synchronizing files between |
|configurations |computers, and Direct Cable |
| |Connection for directly linking |
| |two computers, plus other built-in|
| |communications applications |
| |Remote mail and deferred printing,|
| |for working away from the main |
| |office |
| |Automatic configuration for PCMCIA|
| |cards, and |
| |for all components with Plug and |
| |Play-compliant hardware |
| |User profiles to ensure a custom |
| |desktop for each user, no matter |
| |where users log on to the network |
| |For information, see Chapter 19, |
| |ΓÇ£Devices,ΓÇ¥ and Chapter 28, |
| |ΓÇ£Dial-Up Networking and Mobile |
| |Computing .ΓÇ¥ |
Other Optional Windows 95 Features (continued)
| | |
|Windows 95 feature|Decisions and issues |
| | |
|Use other |Depends on your existing services |
|Windows 95 |and needs. In general, if client |
|value-added |computers have the hard disk space|
|features |and use a utility or an |
|To enable other |application with the same |
|Windows 95 |capabilities from another vendor, |
|ease-of-use |you should install |
|innovations and |the new features and test their |
|capabilities such |value. |
|as The Microsoft |These features are not installed |
|Network and |by default but can |
|Microsoft Fax |be specified during Setup or |
| |installed later: |
| |Microsoft Fax for fax receipt and |
| |transmission |
| |The Microsoft Network for online |
| |services |
| |For information, see Chapter 26, |
| |ΓÇ£Electronic Mail and Microsoft |
| |Exchange,ΓÇ¥ Chapter 27, ΓÇ£Microsoft |
| |Fax,ΓÇ¥ and Chapter 29, ΓÇ£The |
| |Microsoft Network.ΓÇ¥ |
The following will be provided in the final version.
Specify the Preferred Network Client Configuration
| | | | |
|Task |Team |Start |Duration|
| | |week | |
| | | | |
|Decide on configuration layout. | | | |
|Evaluate key features | | | |
|Evaluate recommended features | | | |
|Evaluate optional features | | | |
Conduct the Lab Test
Using the network client configuration that you have developed on paper,
along with the people and tools assembled earlier for the Planning team,
proceed with installing the configuration in the lab for testing and
evaluation. Because only the client-computer configuration is being
installed (server installation is described in the following section), this
test only determines whether the preferred configuration performs as
expected, and whether it is compatible with your current applications and
processes.
Depending on how the test installation proceeds, it may be necessary to
modify
the configuration, by either adding or removing selected features. If more
than
one configuration is being considered, side-by-side evaluations of
different configurations can be performed to help determine which one works
best.
The tasks in the following checklist apply for each computer used to
install a
client configuration. For step-by-step instructions on installing and
selecting features, see Chapter 3, ΓÇ£Introduction to Windows 95 Setup.ΓÇ¥
Conduct the Lab Test
| | | | |
|Task |Team |Start |Duration|
| | |week | |
| | | | |
|1: Before running Windows 95 Setup, |Installati|Week 4 |0.1 day |
|make sure that the computer meets your|on | | |
|company’s standards and the Windows 95| | | |
|minimum standards for operation ΓÇö at | | | |
|least a | | | |
|4-MB 386DX or better. If not, perform | | | |
|the hardware upgrades now. | | | |
|2: Defragment the hard disk and scan|Installati|Week 4 |0.1 day |
|it for viruses. |on | | |
|3: Back up and verify key data and |Installati|Week 4 |0.1 day |
|configuration files, such |on | | |
|as INI, AUTOEXEC.BAT, and CONFIG.SYS | | | |
|files. Also back up the Windows and | | | |
|DOS directories, and all files in the | | | |
|root directory. Make a system startup | | | |
|disk with COMMAND.COM, SYS.COM, and | | | |
|FDISK.EXE on it. | | | |
|4: Ensure that the current network |Installati|Week 4 |1 day |
|client software is functioning |on | | |
|properly and, referring to the | | | |
|checklist of inventoried applications,| | | |
|ensure that all important applications| | | |
|operate correctly. | | | |
|5: Install Windows 95 on the test |Planning, |Week 4 |1 day |
|computer in the lab, using your |Installati| | |
|preferred client configuration. |on | | |
|6: Test the installation: |Planning, |Week 4 |2 days |
|Can you connect to and browse the |Installati| | |
|network? |on | | |
|Can you print both locally and across | | | |
|the network? | | | |
|Can you perform the core operations of| | | |
|each appli | | | |
|cation locally and on the network | | | |
|(including opening, | | | |
|closing, and printing)? | | | |
|Can you shut down successfully? | | | |
|7: Optionally, if you have several |Installati|Week 5 |2 days |
|test computers, compare your old |on, | | |
|client configuration under Windows 3.x|Planning | | |
|and your new preferred configuration. | | | |
|How do the two compare in terms | | | |
|of the following: | | | |
|Functionality for administering the | | | |
|computer and using it for common | | | |
|tasks? | | | |
|Performance for local disk and network| | | |
|actions? | | | |
|Ease of use for performing common | | | |
|tasks? | | | |
|Stability of the two computers under | | | |
|stress? | | | |
|Compatibility with applications and | | | |
|hardware? | | | |
|8: If the specified client |Planning, |Week 5 |As |
|configuration did not work as |Installati| |required|
|expected, modify and document the |on | | |
|differences until a working preferred | | | |
|client configuration is installed. | | | |
|9: Perform a complete restoration of|Installati|Week 5 |1 day |
|operating system files and system |on | | |
|capabilities for your old client | | | |
|configuration on the computer running | | | |
|Windows 95. | | | |
|10: Evaluate the restoration process |Installati|Week 5 |0.5 day |
|for problems. Document |on, | | |
|the process and the modifications |Planning | | |
|made. | | | |
|11: Install the preferred |Installati|Week 5 |3 days |
|configuration on a wider variety of |on, | | |
|hardware, with your team assisting in |Planning | | |
|performing the installations. | | | |
Plan the Pilot Rollout
The previous phase helped to determine the best client configuration for
Windows 95. In this phase, appointed teams will determine the best methods
for automatically installing the specified configuration for a pilot or
trial rollout. Planning for this pilot program involves creating the
automated installation process, determining the logistics of testing, and
preparing a training plan for users.
Automating the installation is a key step in reducing the cost of
migration. By creating a setup script with predetermined answers for
installation questions,
the installation process can run from start to finish without user
intervention. It
is also possible to ΓÇ£pushΓÇ¥ the installation from the server, so that you
can install Windows 95 on an individual personal computer without ever
touching the computer. This automation work is done in the lab, prior to
conducting the pilot rollout.
Plan the Pilot Rollout
| | | | |
|Task |Team |Start |Duration|
| | |week | |
| | | | |
|1: Use Server-based Setup to install|Planning, |Week 6 |1 day |
|Windows 95 source |Installati| | |
|files on a server. Make setup choices |on | | |
|based on your client configuration, | | | |
|including whether you will run a | | | |
|shared copy of Windows 95 from the | | | |
|server, or run Windows 95 locally on | | | |
|the client computer. Perform the | | | |
|following steps: | | | |
|Set up the distribution server | | | |
|Set up the client from the network | | | |
|See Chapter 2, Corporate | | | |
|Implementation Strategy, for | | | |
|step-by-step instructions. Document | | | |
|any changes to this process. | | | |
|2: Create and test an automated |Planning, |Week 6 |2 days |
|installation by creating a setup |Installati| | |
|script to predefine settings for |on | | |
|Setup. Document the key parts of the | | | |
|setup script that vary by | | | |
|installation. | | | |
|3: Determine and test how you will |Planning, |Week 6 |3 days |
|push the installation from the server |Installati| | |
|without having to touch the client |on | | |
|computers. (See Chapter 5, ΓÇ£Custom, | | | |
|Automated, and Push InstallationsΓÇ¥) | | | |
|Options: | | | |
|Modify login scripts on the server. | | | |
|Use management software such as | | | |
|Microsoft Systems Management Server. | | | |
|Send a setup script (batch file) that | | | |
|runs Windows 95 | | | |
|Setup as an embedded link in an | | | |
|electronic mail message. | | | |
|Document the process for the rest of | | | |
|the Installation team. | | | |
Plan the Pilot Rollout (continued)
| | | | |
|Task |Team |Start |Duration|
| | |week | |
| | | | |
|4: Evaluate the Windows 95 |Planning, |Week 7 |2 days |
|installation process for opportunities|Executive | | |
|to upgrade or improve your | | | |
|organizationΓÇÖs existing technology | | | |
|infrastructure. For example, a system | | | |
|management software tool can help you | | | |
|administer computers on the network | | | |
|more easily, and it can help with the | | | |
|push installation process. | | | |
|5: Document the logistics of the |Installati|Week 7 |3 days |
|pilot installation, such as the total |on, | | |
|time for installation, the new |Planning | | |
|software or tools to be purchased, the| | | |
|group selected as the pilot users, and| | | |
|the scheduling of specific | | | |
|installations. This can take the form | | | |
|of a checklist. | | | |
|6: Prepare a memo for your users to |Planning |Week 7 |1 day |
|clearly explain how the installation | | | |
|process will affect their daily work | | | |
|schedule and describe the differences | | | |
|they will see after the installation | | | |
|is completed. | | | |
|7: Establish a support plan for the |Planning, |Week 7 |5 days |
|pilot user group. This includes the |Support | | |
|names and phone numbers of persons to | | | |
|contact for assistance, a short list | | | |
|of the top questions and answers, and | | | |
|troubleshooting tips. | | | |
|8: Prepare a user training course |Planning, |Week 6 |5 days |
|(or hire a training vendor |Support, | | |
|to prepare one). Use the Windows 95 |Training | | |
|online tutorial and Introducing | | | |
|Microsoft Windows 95 to ΓÇ£jump-startΓÇ¥ | | | |
|your training efforts. | | | |
|9: Set up the lab or classroom with |Training |Week 7 |2 days |
|computers for training. | | | |
|10: Edit the Windows 95 Help file (if |Planning, |Week 8 |4 days |
|appropriate) to include |Support | | |
|any company-specific information. | | | |
|Repeat this after the | | | |
|pilot rollout is completed. | | | |
Conduct the Pilot Rollout
The goal of the pilot program is to test your automated installation in
everyday use among a limited group of users (for example, between 15 and
50). This process helps to identify problems that may impede or delay the
deployment process, and
to determine what resources youΓÇÖll require for the final, company-wide
rollout.
The pilot rollout also sets the tone for the rest of the deployment
process; a successful pilot rollout helps other installations to run
smoothly by stimulating
the cooperation and enthusiasm of your users.
Conduct the Pilot Rollout
| | | | |
|Task |Team |Start |Duration |
| | |week | |
| | | | |
|1: Select a pilot user group that is|Planning |Week 8 |2 days |
|willing and able (particularly in | | | |
|terms of their workload) to handle the| | | |
|installation process. | | | |
|2: Train the users. |Training |Week 8 |5 days |
|3: Back up the Windows and DOS |Installat|Week 9 |5 days |
|directories and the files on the root |ion | | |
|directory of the test computers. | | | |
|4: Perform the installation in the |Installat|Week 9 |10 days |
|same manner that you expect to install|ion | | |
|Windows 95 throughout the company. | | | |
|5: Have your technicians on-site for|Support |Week 9 |15 days |
|the initial installations to document | | | |
|the process and problems, and to | | | |
|support the users. Have other | | | |
|technicians monitor time and all | | | |
|measurable factors in the installation| | | |
|process. | | | |
|6: Ensure that all computers are ΓÇ£up|Planning,|Week 11 |3 days |
|and runningΓÇ¥ as expected. Make note of|Installat| | |
|possible improvements to the |ion, | | |
|installation, training, or support, |Support | | |
|where appropriate. | | | |
|7: Survey members of the pilot user |Planning |Week 12 |3 days |
|group about their satis-faction with | | | |
|the installation process and take | | | |
|feedback on what could have been done | | | |
|better. | | | |
|8: Continue to monitor the pilot |Support, |Week 11 |5 days |
|installation for a week to ensure that|Planning | | |
|everything continues to run smoothly. | | | |
|9: Prepare a checklist of issues to |Support, |Week 11 |5 days |
|resolve for the final rollout. Include|Planning | | |
|in this checklist the areas identified| | | |
|in step 6 as needing improvement and | | | |
|the results from the user survey. | | | |
|During preparation for final rollout, | | | |
|check off items on this list as they | | | |
|are resolved. | | | |
|10: If the pilot program did not run |Planning,|Week 12 |See ΓÇ£Plan|
|smoothly or user feedback was poor, |Installat| |the Pilot|
|conduct additional pilot installations|ion | |RolloutΓÇ¥ |
|until the process works well. | | | |
Finalize the Rollout Plan
The results of the pilot installation provide the basis for developing a
final plan for rollout. Using the actual time and resource requirements
from the smaller-scale pilot rollout, teams make projections for time and
resources, corresponding to the company-wide scope of the final rollout. If
additional resources are required, these should be identified and acquired
at this time. In addition, company policies and standards regarding
computer and network use should be updated in accordance with the
Windows 95 implementation.
Finalize the Rollout Plan
| | | | |
|Task |Team |Start |Duration|
| | |week | |
| | | | |
|1: Determine your rollout goals ΓÇö |Planning, |Week 12 |5 days |
|specifically the number of computers |Executive | | |
|on which you will install Windows 95 | | | |
|and the time expected for completion. | | | |
|2: Budget the resources, in terms of|Planning |Week 12 |3 days |
|personnel and tools, required to meet | | | |
|your goals. | | | |
|3: If necessary, present the budget |Executive,|Week 13 |2 days |
|and obtain approval for |Planning | | |
|the resources and the rollout process.| | | |
|4: Hire and train the extended |Training, |Week 13 |10 days |
|Installation team and purchase |Installati| | |
|the additional software or tools |on | | |
|needed. | | | |
|5: Update the companyΓÇÖs hardware and|Planning |Week 13 |2 days |
|software standards lists. | | | |
|6: Update the companyΓÇÖs policies and|Planning |Week 13 |2 days |
|practices manuals or guidelines for | | | |
|use of computers and the network. | | | |
|7: Notify your users that company |Planning |Week 13 |1 day |
|standards and policies for computer | | | |
|use will be enforced prior to the | | | |
|installation and that they must bring | | | |
|their computers into compliance. | | | |
|8: If appropriate, edit the |Planning, |Week 14 |3 days |
|Windows 95 Help file to add |Support | | |
|company-specific Help for | | | |
|line-of-business applications, | | | |
|and to remove unwanted information | | | |
|about the capabilities you plan to | | | |
|disable in Windows 95. | | | |
|9: For each computer, create a |Installati|Week 13 |2 days |
|template as a database for documenting|on | | |
|and tracking any system problems or | | | |
|deficiencies that require further | | | |
|attention. | | | |
|10: Post the updated template to a |Installati|Week 13 |2 days |
|central network location. |on | | |
Roll Out Windows 95!
After the extensive research, planning, testing, and analysis performed in
the previous phases, the final step in the deployment process is rolling
out the Windows 95 installation to the entire company.
Roll Out Windows 95
| | | | |
|Task |Team |Start |Duration |
| | |week | |
| | | | |
|1: Set up the distribution servers |Installat|Week 15 |1 day |
|by using the Server-based Setup and |ion | | |
|configuring the system policy files. | | | |
|2: Customize the server |Installat|Week 15 |2 days |
|installation by adding or removing |ion | | |
|the appropriate files, including the | | | |
|MSBATCH.INF file. | | | |
|3: Notify the users of the upcoming|Planning |Week 15 |1 day |
|installation. | | | |
|4: Train the users on Windows 95. |Training |Week 16 |As |
| | | |required |
|5: If needed, upgrade the hardware |Installat|Week 16 |As |
|on the client computers and remove |ion | |required |
|any software not complying with | | | |
|company policy. | | | |
|6: If needed, back up critical data|Installat|Week 16 |As |
|and configuration files on the client|ion | |required |
|computers. | | | |
|7: If needed, defragment the client|Installat|Week 16 |As |
|hard disks. |ion | |required |
|8: Optionally, you can temporarily |Planning |Week 17 |As |
|reset the user password and ID for | | |required |
|each computer, to allow your | | | |
|technicians easy access to the client| | | |
|computer and ensure that the login | | | |
|scripts and environment operate | | | |
|correctly. | | | |
|9: Ensure that the client computers|Installat|Week 17 |As |
|are fully operational and the |ion | |required |
|real-mode network, if present, is | | | |
|running. | | | |
|10: Prepare the client computers for |Installat|Week 18 |As |
|the push installation process: edit |ion | |required |
|the login scripts; run the management| | | |
|software; or send the setup script, | | | |
|by electronic mail, | | | |
|to the user. | | | |
|11: Initiate the installation by |Installat|Week 18 |As |
|having the user log on, double-click |ion | |required |
|the setup script file, and so on. | | | |
For details of each task in the deployment checklists, see Chapter 2,
ΓÇ£Corporate Implementation Strategy.ΓÇ¥ For step-by-step instructions on how
to set up, maintain, and use Windows 95 in a corporate environment, see the
appropriate chapters of the Resource Kit.
(.txt)
(.txt)